Doorbell communities

ABSTRACT

Doorbells can send data to each other to enable a first doorbell user to warn a second doorbell user regarding a suspicious visitor. A first user can indicate a first trait of a visitor via a first remote computing device. The first user can create a user group to enable the members of the user group to use their doorbells to take pictures of suspicious visitors and to send the pictures of the suspicious visitors to other members of the user group.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of and is a continuation-in-part ofU.S. Non-Provisional patent application Ser. No. 14/861,613; filed Sep.22, 2015; entitled DOORBELL COMMUNICATION SYSTEMS AND METHODS; andhaving an attorney docket number SKYBELL.063A. The entire contents ofU.S. patent application Ser. No. 14/861,613 are incorporated byreference herein. U.S. Non-Provisional patent application Ser. No.14/861,613 claims the benefit of and is a continuation-in-part of U.S.Non-Provisional patent application Ser. No. 14/748,054 (issued as U.S.Pat. No. 9,230,424); filed Jun. 23, 2015; entitled DOORBELL COMMUNITIES;and having an attorney docket number SKYBELL.047A. The entire contentsof U.S. patent application Ser. No. 14/748,054 are incorporated byreference herein.

The entire contents of the following application are incorporated byreference herein: U.S. Provisional Patent Application No. 62/143,032;filed Apr. 4, 2015; and entitled DOORBELL COMMUNITIES.

The entire contents of the following applications are incorporated byreference herein: U.S. Nonprovisional patent application Ser. No.14/612,376; filed Feb. 3, 2015; and entitled DOORBELL COMMUNICATIONSYSTEMS AND METHODS; U.S. Nonprovisional patent application Ser. No.14/502,601; filed Sep. 30, 2014; and entitled DOORBELL COMMUNICATIONSYSTEMS AND METHODS; U.S. Nonprovisional patent application Ser. No.14/492,809; filed Sep. 22, 2014; and entitled DOORBELL COMMUNICATIONSYSTEMS AND METHODS; U.S. Nonprovisional patent application Ser. No.14/275,811; filed May 12, 2014; and entitled DOORBELL COMMUNICATIONSYSTEMS AND METHODS; U.S. Nonprovisional patent application Ser. No.14/142,839; filed Dec. 28, 2013; and entitled DOORBELL COMMUNICATIONSYSTEMS AND METHODS; U.S. Nonprovisional patent application Ser. No.14/099,888; filed Dec. 6, 2013; and entitled DOORBELL COMMUNICATIONSYSTEMS AND METHODS; and U.S. Nonprovisional patent application Ser. No.14/098,772; filed Dec. 6, 2013; and entitled DOORBELL COMMUNICATIONSYSTEMS AND METHODS.

The entire contents of the following application are incorporated byreference herein: International Application No. PCT/US14/47622; filedJul. 22, 2014 with the U.S. Patent and Trademark Office; and entitledDOORBELL COMMUNICATION SYSTEMS AND METHODS.

The entire contents of the following application are incorporated byreference herein: International Application No. PCT/US14/53506; filedAug. 29, 2014 with the U.S. Patent and Trademark Office; and entitledDOORBELL COMMUNICATION SYSTEMS AND METHODS.

BACKGROUND Field

Various embodiments disclosed herein relate to doorbells. Certainembodiments relate to doorbell communities.

Description of Related Art

Doorbells can enable a person located outside of an entry point, such asa door, to alert a person inside of an entry point that someone outsidewould like to talk to someone inside. Doorbells sometimes include abutton located near a door, such as a front door, side door, or backdoor of a home, office, dwelling, warehouse, building, or structure.Doorbells are sometimes used near a gate or some other entrance to apartially enclosed area. Pushing the doorbell sometimes causes a chimeor other alerting sound to be emitted.

SUMMARY

Data from multiple doorbells can be shared among a doorbell user group.Information regarding a visitor to a first building can be shared withother members of the doorbell user group. For example, a homeowner canshare information from her doorbell with neighbors' remote computingdevices via the doorbell user group even though the neighbors' remotecomputing devices are not configured to receive visitor alerts from thehomeowner's doorbell each time the homeowner's doorbell detects avisitor (e.g., via motion detection or button press detection). Someembodiments include the homeowner (e.g., a user) choosing to send afirst visit information (regarding a first visitor) to neighbor's remotecomputing devices and choosing not to send a second visit information(regarding a second visitor) to neighbor's remote computing devices.Thus, the system enables a user to selectively decide what visitinformation to share with members of the doorbell user group.

In some embodiments, the doorbell system can comprise a first remotecomputing device communicatively coupled to a first doorbell having afirst camera. The method for using the doorbell system can comprisesending a first picture, taken by the first doorbell, of a first visitorto the first remote computing device. A doorbell user group can becreated and can comprise a first user, of the first remote computingdevice, and a second user, of a second remote computing device. A secondremote computing device can be communicatively coupled to a seconddoorbell, but may not necessarily be communicatively coupled to thefirst doorbell. The method for using the doorbell system can comprisesharing the first picture of the first visitor with the doorbell usergroup, such that the second remote computing device can receive thefirst picture.

In several embodiments, the first remote computing device may not becommunicatively coupled to the second doorbell. The method can comprisereceiving, by the first remote computing device, a second picture takenby the second doorbell. The second picture can be taken in response tothe second doorbell sending the second picture to a database. Thedatabase can be configured to provide visitor information to thedoorbell user group.

In some embodiments, the method for using the doorbell system cancomprise the indication of a first trait of the first visitor via thefirst remote computing device. The method can comprise sharing the firstpicture of the first visitor with the doorbell user group in response tothe first trait of the first visitor.

In several embodiments, the method can comprise the indication of afirst trait of the first visitor via the first remote computing device.The method can send the first trait and the first picture of the firstvisitor to a database. The database can be configured to provideinformation regarding the first visitor to the doorbell user group. Themethod can provide a time, at which the first visitor visited the firstdoorbell, to the database.

In some embodiments, the first remote computing device cannot becommunicatively coupled to the second doorbell. The method for using thedoorbell system can comprise receiving, by the first remote computingdevice, data from the doorbell user group regarding the second doorbell.The second doorbell can comprise a second camera. In some cases, a thirddoorbell can comprise a third camera. The second doorbell can be coupledto a second building, and the third doorbell can be coupled to a thirdbuilding.

In several embodiments, the doorbell system can comprise a databaseconfigured to share visitor information with the doorbell user group.The method can comprise selecting, via the first remote computingdevice, to receive the visitor information from at least one of thesecond doorbell and the third doorbell.

In some embodiments, the first doorbell can be coupled to a firstbuilding. The first building, the second building, and the thirdbuilding can be located apart from each other. Receiving the data cancomprise receiving the visitor information from a different locationthan a first location of the first building.

In several embodiments, the first picture can comprise a first video.The first picture can also be a still image (although many users preferpictures that are videos).

In some embodiments, creating the doorbell user group can compriseadding a first email address and a second email address to a database.The first email address can be associated with the first doorbell, andthe second email address can be associated with the second doorbell.

In several embodiments, the method for using the doorbell system cancomprise displaying a map on the first remote computing device. The mapcan display a second location of the second doorbell and a thirdlocation of a third doorbell. The method can comprise displayinginformation, regarding the second doorbell, in response to selecting amap icon, representing the second doorbell, while the map icon isdisplayed on the first remote computing device. Selecting the map iconcan be used to add the second user of the second doorbell to thedoorbell user group. Methods can include sending an invitation (to jointhe user group) to the second user in response to selecting the seconddoorbell on the map.

In some embodiments, the method can comprise selecting a first button onthe first remote computing device to alert law enforcement and/or toalert the doorbell user group.

In several embodiments, the first doorbell can be coupled to a firstbuilding. The second doorbell can be coupled to a second building. Athird doorbell can be coupled to a third building. The buildings can belocated remotely relative to each other. The method can compriseanalyzing information collected from the first, second, and thirddoorbells, and then sending an alert in response to analytics based onthe information. Analytics can include visitor identity, visit frequency(e.g., during a timeframe), time of visits, and facial recognition ofvisitors.

In some embodiments, a method of using a doorbell system can comprisecoupling a first doorbell having a first camera to a first building,configuring the first doorbell to wirelessly communicate with a firstremote computing device, and joining, by the first remote computingdevice, a doorbell user group. The doorbell user group can comprise asecond user and a third user. The second user can comprise a seconddoorbell having a second camera coupled to a second building. A thirduser can comprise a third doorbell having a third camera coupled to athird building. The second doorbell can be configured to wirelesslycommunicate with a second remote computing device.

In several embodiments, the method of using the doorbell system cancomprise receiving, by the first remote computing device, a firstvisitor picture. The second doorbell or the third doorbell can take thefirst visitor picture. The method can comprise receiving, from thedoorbell user group by the first remote computing device, a firstvisitor picture taken by the second doorbell. The first remote computingdevice may not be communicatively coupled to the second doorbell.

In some embodiments, the method can comprise receiving, by the firstremote computing device, a first trait. The first trait can be regardinga first visitor in response to the second user inputting the first traitinto the second remote computing device.

In several embodiments, the method of using the doorbell system cancomprise taking a second visitor picture, by the first doorbell, andsending the second visitor picture to the doorbell user group. Thesecond remote computing device can display the second visitor picture,even though the second remote computing device may not becommunicatively coupled to the first doorbell.

In some embodiments, the doorbell user group can comprise a databasehaving a first visitor picture taken by the second doorbell of thesecond building. The method can comprise taking, by the first doorbellof the first building, a second visitor picture. The method can comprisedetermining, by a portion of the doorbell system, that the first visitorpicture and the second visitor picture show a visitor.

In several embodiments, the method can comprise labeling the visitorwith solicitor information. The members of the doorbell user group canthen see the first visitor picture associated with the solicitorinformation. The method can comprise alerting the members regarding atleast a portion of the solicitor information.

In some embodiments, the method can comprise receiving a solicitoralert. The alert can be in response to the second doorbell, of thesecond building, and the third doorbell, of the third building,detecting a visitor.

In several embodiments, the method can comprise adding solicitationinformation regarding the visitor to the doorbell user group.

In some embodiments, the method can comprise sending an alert to membersof the doorbell user group in response to detecting, by a remote burglardetection system, a burglary of the first building.

In several embodiments, a doorbell system can comprise a first doorbellthat can have a first camera that can be coupled to a first building.The first doorbell can be communicatively coupled to a first remotecomputing device. A second doorbell can have a second camera that can becoupled to a second building. The second doorbell can be communicativelycoupled to a second remote computing device. The doorbell system canhave a doorbell user group that can comprise a database that can haveimages taken by the first camera and the second camera. The doorbelluser group can be communicatively coupled to the first remote computingdevice and the second remote computing device.

In some embodiments of the doorbell system, the first doorbell may notbe communicatively coupled to the second remote computing device. Thesecond doorbell may not be communicatively coupled to the first remotecomputing device. The system can be configured such that the firstremote computing device can receive a first visitor picture taken by thesecond doorbell via the doorbell user group.

In several embodiments, the doorbell system can comprise a secondvisitor picture taken by the first doorbell. The picture can bedisplayed by the second remote computing device.

In some embodiments, the doorbell system can comprise a remote sensor.The remote sensor can be configured to monitor the first building andcan detect an unauthorized building intrusion. An alert can be sent tothe doorbell user group in response to the remote sensor detecting theunauthorized building intrusion.

In several embodiments, the system can comprise a solicitor alert. Asolicitor alert can be sent to the doorbell user group in response to avisitor being detected by the first doorbell, at the first building, andby the second doorbell, at the second building.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages are described belowwith reference to the drawings, which are intended to illustrate, butnot to limit, the invention. In the drawings, like reference charactersdenote corresponding features consistently throughout similarembodiments.

FIG. 1 illustrates a front view of a doorbell system, according to someembodiments.

FIG. 2 illustrates a front view of a computing device running softwareto communicate with the doorbell from FIG. 1, according to someembodiments.

FIG. 3 illustrates a diagrammatic view of an embodiment in which thedoorbell from FIG. 1 is connected to a building, according to someembodiments.

FIG. 4 illustrates a back view of the doorbell from FIG. 1 without amounting bracket, according to some embodiments.

FIG. 5 illustrates a diagrammatic view of a group of doorbells,according to some embodiments.

FIG. 6 illustrates a front view of a remote computing device displayinga map, according to some embodiments.

FIG. 7 illustrates a diagrammatic view of picture being communicated,according to some embodiments.

FIG. 8 illustrates a diagrammatic view of a doorbell that iscommunicatively coupled to multiple remote computing devices, accordingto some embodiments.

FIG. 9 illustrates a diagrammatic view of a remote computing device thatis communicatively coupled to multiple doorbells, according to someembodiments.

FIGS. 10 and 11 illustrate diagrammatic views of doorbell user groups,according to some embodiments.

DETAILED DESCRIPTION

Although certain embodiments and examples are disclosed below, inventivesubject matter extends beyond the specifically disclosed embodiments toother alternative embodiments and/or uses, and to modifications andequivalents thereof. Thus, the scope of the claims appended hereto isnot limited by any of the particular embodiments described below. Forexample, in any method or process disclosed herein, the acts oroperations of the method or process may be performed in any suitablesequence and are not necessarily limited to any particular disclosedsequence. Various operations may be described as multiple discreteoperations in turn, in a manner that may be helpful in understandingcertain embodiments; however, the order of description should not beconstrued to imply that these operations are order dependent.Additionally, the structures, systems, and/or devices described hereinmay be embodied as integrated components or as separate components.

For purposes of comparing various embodiments, certain aspects andadvantages of these embodiments are described. Not necessarily all suchaspects or advantages are achieved by any particular embodiment. Thus,for example, various embodiments may be carried out in a manner thatachieves or optimizes one advantage or group of advantages as taughtherein without necessarily achieving other aspects or advantages as mayalso be taught or suggested herein.

System Embodiments

Communication systems can provide a secure and convenient way for aremotely located individual to communicate with a person who isapproaching a sensor, such as a proximity sensor or motion sensor, orwith a person who rings a doorbell, which can be located in a doorway,near an entrance, or within 15 feet of a door. Some communicationsystems allow an individual to hear, see, and talk with visitors whoapproach at least a portion of the communication system and/or press abutton, such as a doorbell's button. For example, communication systemscan use a computing device to enable a remotely located person to see,hear, and/or talk with visitors. Computing devices can includecomputers, laptops, tablets, mobile devices, smartphones, cellularphones, and wireless devices (e.g., cars with wireless communication).Example computing devices include the iPhone, iPad, iMac, MacBook Air,and MacBook Pro made by Apple Inc. Communication between a remotelylocated person and a visitor can occur via the Internet, cellularnetworks, telecommunication networks, and wireless networks.

Referring now to FIG. 1, doorbell systems can be a portion of a smarthome hub. In some embodiments, the doorbell system 200 forms the core ofthe smart home hub. For example, the various systems described hereinenable complete home automation. In some embodiments, the doorbell 202controls various electrical items in a home (e.g., lights, airconditioners, heaters, motion sensors, garage door openers, locks,televisions, computers, entertainment systems, pool monitors, elderlymonitors). In some embodiments, the computing device 204 controls thedoorbell 202 and other electrical items in a home (e.g., lights, airconditioners, heaters, motion sensors, garage door openers, locks,televisions, computers, entertainment systems, pool monitors, elderlymonitors).

FIG. 1 illustrates a front view of a communication system embodiment.The doorbell system 200 can include a doorbell 202 (e.g., a securitysystem) and a computing device 204. Although the illustrated doorbell202 includes many components in one housing, several doorbellembodiments include components in separate housings. The doorbell 202can include a camera assembly 208 and a doorbell button 212. The cameraassembly 208 can include a video camera, which in some embodiments is awebcam. The doorbell 202 can include a diagnostic light 216 and a powerindicator light 220. In some embodiments, the diagnostic light 216 is afirst color (e.g., blue) if the doorbell 202 and/or the doorbell system200 is connected to a wireless Internet network and is a second color(e.g., red) if the doorbell 202 and/or the doorbell system 200 is notconnected to a wireless Internet network. In some embodiments, the powerindicator 220 is a first color if the doorbell 202 is connected to apower source. The power source can be supplied by the building to whichthe doorbell 202 is attached. In some embodiments, the power indicator220 is a second color or does not emit light if the doorbell 202 is notconnected to the power source.

The doorbell 202 can include an outer housing 224, which can be waterresistant and/or waterproof. The outer housing can be made from metal orplastic, such as molded plastic with a hardness of 60 Shore D. In someembodiments, the outer housing 224 is made from brushed nickel oraluminum.

Rubber seals can be used to make the outer housing 224 water resistantor waterproof. The doorbell 202 can be electrically coupled to a powersource, such as wires electrically connected to a building's electricalpower system. In some embodiments, the doorbell 202 includes a batteryfor backup and/or primary power.

Wireless communication 230 can enable the doorbell 202 to communicatewith the computing device 204. Some embodiments enable communication viacellular and/or WiFi networks. Some embodiments enable communication viathe Internet. Several embodiments enable wired communication between thedoorbell 202 and the computing device 204. The wireless communication230 can include the following communication means: radio, WiFi (e.g.,wireless local area network), cellular, Internet, Bluetooth,telecommunication, electromagnetic, infrared, light, sonic, andmicrowave. Other communication means are used by some embodiments. Insome embodiments, such as embodiments that include telecommunication orcellular communication means, the doorbell 202 can initiate voice callsor send text messages to a computing device 204 (e.g., a smartphone, adesktop computer, a tablet computer, a laptop computer).

Several embodiments use near field communication (NFC) to communicatebetween the computing device 204 and the doorbell 202. The doorbell 202and/or the computing device 204 can include a NFC tag. Some NFCtechnologies include Bluetooth, radio-frequency identification, and QRcodes.

Some embodiments include computer software (e.g., application software),which can be a mobile application designed to run on smartphones, tabletcomputers, and other mobile devices. Software of this nature issometimes referred to as “app” software. Some embodiments includesoftware designed to run on desktop computers and laptop computers.

The computing device 204 can run software with a graphical userinterface. The user interface can include icons or buttons. In someembodiments, the software is configured for use with a touch-screencomputing device such as a smartphone or tablet.

FIG. 2 illustrates a computing device 204 running software. The softwareincludes a user interface 240 displayed on a display screen 242. Theuser interface 240 can include a doorbell indicator 244, which canindicate the location of the doorbell that the user interface isdisplaying. For example, a person can use one computing device 204 tocontrol and/or interact with multiple doorbells, such as one doorbelllocated at a front door and another doorbell located at a back door.Selecting the doorbell indicator 244 can allow the user to chooseanother doorbell (e.g., the back door's doorbell rather than the frontdoor's doorbell).

The user interface 240 can include a connectivity indicator 248. In someembodiments, the connectivity indicator can indicate whether thecomputing device is in communication with a doorbell, the Internet,and/or a cellular network. The connectivity indicator 248 can alert theuser if the computing device 204 has lost its connection with thedoorbell 202; the doorbell 202 has been damaged; the doorbell 202 hasbeen stolen; the doorbell 202 has been removed from its mountinglocation; the doorbell 202 has lost electrical power; and/or if thecomputing device 204 cannot communicate with the doorbell 202. In someembodiments, the connectivity indicator 248 alerts the user of thecomputing device 204 by flashing, emitting a sound, displaying amessage, and/or displaying a symbol.

In some embodiments, if the doorbell 202 loses power, loses connectivityto the computing device 204, loses connectivity to the Internet, and/orloses connectivity to a remote server, a remote server 206 sends analert (e.g., phone call, text message, image on the user interface 240)regarding the power and/or connectivity issue. In several embodiments,the remote server 206 can manage communication between the doorbell 202and the computing device. In some embodiments, information from thedoorbell 202 is stored by the remote server 206. In several embodiments,information from the doorbell 202 is stored by the remote server 206until the information can be sent to the computing device 204, uploadedto the computing device 204, and/or displayed to the remotely locatedperson via the computing device 204. The remote server 206 can be acomputing device that stores information from the doorbell 202 and/orfrom the computing device 204. In some embodiments, the remote server206 is located in a data center.

In some embodiments, the computing device 204 and/or the remote server206 attempts to communicate with the doorbell 202. If the computingdevice 204 and/or the remote server 206 is unable to communicate withthe doorbell 202, the computing device 204 and/or the remote server 206alerts the remotely located person via the software, phone, text, adisplayed message, and/or a website. In some embodiments, the computingdevice 204 and/or the remote server 206 attempts to communicate with thedoorbell 202 periodically; at least every five hours and/or less thanevery 10 minutes; at least every 24 hours and/or less than every 60minutes; or at least every hour and/or less than every second.

In some embodiments, the server 206 can initiate communication with thecomputing device 204 and/or with the doorbell 202. In severalembodiments, the server 206 can initiate, control, and/or blockcommunication between the computing device 204 and the doorbell 202.

In several embodiments, a user can log in to an “app,” website, and/orsoftware on a computing device (e.g., mobile computing device,smartphone, tablet, desktop computer) to adjust the doorbell settingsdiscussed herein.

In some embodiments, a computing device can enable a user to watch livevideo and/or hear live audio from a doorbell due to the user's requestrather than due to actions of a visitor. Some embodiments include acomputing device initiating a live video feed (or a video feed that isless than five minutes old).

In some embodiments, the user interface 240 displays an image 252 suchas a still image or a video of an area near and/or in front of thedoorbell 202. The image 252 can be taken by the camera assembly 208 andstored by the doorbell 202, server 206, and/or computing device 204. Theuser interface 240 can include a recording button 256 to enable a userto record images, videos, and/or sound from the camera assembly 208,microphone of the doorbell 202, and/or microphone of the computingdevice 204.

In several embodiments, the user interface 240 includes a picture button260 to allow the user to take still pictures and/or videos of the areanear and/or in front of the doorbell 202. The user interface 240 canalso include a sound adjustment button 264 and a mute button 268. Theuser interface 240 can include camera manipulation buttons such as zoom,pan, and light adjustment buttons. In some embodiments, the cameraassembly 208 automatically adjusts between Day Mode and Night Mode. Someembodiments include an infrared camera and/or infrared lights toilluminate an area near the doorbell 202 to enable the camera assembly208 to provide sufficient visibility (even at night).

In some embodiments, buttons include diverse means of selecting variousoptions, features, and functions. Buttons can be selected by mouseclicks, keyboard commands, or touching a touch screen. Many embodimentsinclude buttons that can be selected without touch screens.

In some embodiments, the user interface 240 includes a quality selectionbutton, which can allow a user to select the quality and/or amount ofthe data transmitted from the doorbell 202 to the computing device 204and/or from the computing device 204 to the doorbell 202.

In some embodiments, video can be sent to and/or received from thecomputing device 204 using video chat protocols such as FaceTime (byApple Inc.) or Skype (by Microsoft Corporation). In some embodiments,these videos are played by videoconferencing apps on the computingdevice 204 instead of being played by the user interface 240.

The user interface 240 can include a termination button 276 to endcommunication between the doorbell 202 and the computing device 204. Insome embodiments, the termination button 276 ends the ability of theperson located near the doorbell 202 (i.e., the visitor) to hear and/orsee the user of the computing device 204, but does not end the abilityof the user of the computing device 204 to hear and/or see the personlocated near the doorbell 202.

In some embodiments, a button 276 is both an answer button (to accept acommunication request from a visitor) and a termination button (to endcommunication between the doorbell 202 and the computing device 204).The button 276 can include the word “Answer” when the system isattempting to establish two-way communication between the visitor andthe user. Selecting the button 276 when the system is attempting toestablish two-way communication between the visitor and the user canstart two-way communication. The button 276 can include the words “EndCall” during two-way communication between the visitor and the user.Selecting the button 276 during two-way communication between thevisitor and the user can terminate two-way communication. In someembodiments, terminating two-way communication still enables the user tosee and hear the visitor. In some embodiments, terminating two-waycommunication causes the computing device 204 to stop showing video fromthe doorbell and to stop emitting sounds recorded by the doorbell.

In some embodiments, the user interface 240 opens as soon as thedoorbell detects a visitor (e.g., senses indications of a visitor). Oncethe user interface 240 opens, the user can see and/or hear the visitoreven before “answering” or otherwise accepting two-way communication, inseveral embodiments.

Some method embodiments include detecting a visitor with a doorbell. Themethods can include causing the user interface to display on a remotecomputing device 204 due to the detection of the visitor (e.g., with orwithout user interaction). The methods can include displaying video fromthe doorbell and/or audio from the doorbell before the user acceptstwo-way communication with the visitor. The methods can includedisplaying video from the doorbell and/or audio from the doorbell beforethe user accepts the visitor's communication request. The methods caninclude the computing device simultaneously asking the user if the userwants to accept (e.g., answer) the communication request and displayingaudio and/or video of the visitor. For example, in some embodiments, theuser can see and hear the visitor via the doorbell before opening ameans of two-way communication with the visitor.

In some embodiments, the software includes means to start the video feedon demand. For example, a user of the computing device might wonder whatis happening near the doorbell 202. The user can open the softwareapplication on the computing device 204 and instruct the application toshow live video and/or audio from the security device 202 even if noevent near the doorbell 202 has triggered the communication.

In several embodiments, the security device 202 can be configured torecord when the security device 202 detects movement and/or the presenceof a person. The user of the computing device 204 can later review allvideo and/or audio records from when the security device 202 detectedmovement and/or the presence of a person.

Referring now to FIG. 1, in some embodiments, the server 206 controlscommunication between the computing device 204 and the doorbell 202,which can be a doorbell with a camera, a microphone, and a speaker. Inseveral embodiments, the server 206 does not control communicationbetween the computing device 204 and the doorbell 202.

In some embodiments, data captured by the doorbell and/or the computingdevice 204 (such as videos, pictures, and audio) is stored by anotherremote device such as the server 206. Cloud storage, enterprise storage,and/or networked enterprise storage can be used to store video,pictures, and/or audio from the doorbell system 200 or from any part ofthe doorbell system 200. The user can download and/or stream stored dataand/or storage video, pictures, and/or audio. For example, a user canrecord visitors for a year and then later can review conversations withvisitors from the last year. In some embodiments, remote storage, theserver 206, the computing device 204, and/or the doorbell 202 can storeinformation and statistics regarding visitors and usage.

FIG. 3 illustrates an embodiment in which a doorbell 202 is connected toa building 300, which can include an entryway 310 that has a door 254.Electrical wires 304 can electrically couple the doorbell 202 to theelectrical system of the building 300 such that the doorbell 202 canreceive electrical power from the building 300. The building can includea door lock 250 to lock the door 254.

A wireless network 308 can allow devices to wirelessly access theInternet. The doorbell 202 can access the Internet via the wirelessnetwork 308. The wireless network 308 can transmit data from thedoorbell 202 to the Internet, which can transmit the data to remotelylocated computing devices 204. The Internet and wireless networks cantransmit data from remotely located computing devices 204 to thedoorbell 202. In some embodiments, a doorbell 202 connects to a home'sWiFi.

As illustrated in FIG. 3, one computing device 204 (e.g., a laptop, asmartphone, a mobile computing device, a television) can communicatewith multiple doorbells 202. In some embodiments, multiple computingdevices 204 can communicate with one doorbell 202.

In some embodiments, the doorbell 202 can communicate (e.g., wirelessly230) with a television 306, which can be a smart television. Users canview the television 306 to see a visitor and/or talk with the visitor.

FIG. 4 illustrates an internal view of the doorbell 202. Doorbells 202can include a chip 480 (e.g., integrated circuits, microprocessor,computer) and a memory 492. Doorbells 202 can also include a microphone484 and a speaker 488. The speaker 488 can comprise a flat speaker and asound chamber 460 configured to amplify an emitted sound. The flatspeaker can be located in the sound chamber. Some doorbell embodimentsinclude a proximity sensor 500. In several embodiments, doorbells 202include a wireless communication module 504, such as a Wi-Fi module. Thecommunication module 504 can have an integrated antenna. In someembodiments, an antenna is contained within the outer housing 224.

The doorbell 202 can include one or more heating elements 508 configuredto regulate the temperature of the doorbell 202. For example, doorbells202 can be used in very cold environments, such as in Alaska. Theheating element 508 can be used in various methods to protecttemperature sensitive portions of the doorbell 202 from cold weather.

While protecting the doorbell 202 from cold weather can be important insome embodiments, protecting visitors from excessive heat can also beimportant in some embodiments. Excessive heat could burn visitors asthey “ring” the doorbell (e.g., press the doorbell button 212 shown inFIG. 10). The doorbell 202 can include a thermometer 512 to enable thesystem to determine the temperature inside a portion of the doorbell 202and/or outside the doorbell 202.

Several embodiments can be configured for 9 to 40 volts alternatingcurrent (“VAC”) and/or 9 to 40 volts direct current (“VDC”). Someembodiments convert input electricity into direct current (DC), such as12 VDC. Several embodiments include a converter 494 for power conversion(e.g., converting electrical energy from one form to another). Theconverter 494 can convert input power (e.g., from wiring in a building)to a suitable power form for the doorbell 202. The power conversion canconvert between AC and DC, change the voltage, and/or change thefrequency. The converter 494 can include a transformer and/or a voltageregulator. In several embodiments, the converter 494 can include an ACto DC converter, a DC to DC converter, a voltage stabilizer, a linearregulator, a surge protector, a rectifier, a power supply unit, aswitch, an inverter, and/or a voltage converter. In some embodiments,the converter 494 converts 50 Hertz (“Hz”) power into 60 Hz power.

The electrical components of the doorbell 202 (e.g., the camera assembly208, the memory 492, the chip 480, the speaker 488, the converter 494,the microphone 484, the lights 458, the rectifier 524, the proximitysensor 500, the communication module 504, the heating element 508, theelectrical connectors 510, the thermometer 512, the image analysissystem 520, and the battery 642) can be electrically coupled to aprinted circuit board (“PCB”) 516 and can receive electrical power fromthe PCB 516.

The PCB 516 and the electrical components of the doorbell 202 can be theelectrical system 456 of the doorbell 202. Additional details regardingthe PCB 516 and the electrical components of the doorbell 202 aredescribed in U.S. Nonprovisional patent application Ser. No. 14/612,376;filed Feb. 3, 2015; and entitled DOORBELL COMMUNICATION SYSTEMS ANDMETHODS. The entire contents of patent application Ser. No. 14/612,376are incorporated by reference herein.

Although some embodiments are described in the context of methods, themethod embodiments can also be formulated as devices and systems.Methods described herein can be applied to the devices and systemsincorporated by references herein.

Systems with Multiple Doorbells

Multiple doorbells can share data to “watch” over a neighborhood byletting people connect with neighbors and share information regardingsuspicious visitors. The shared information can include pictures ofvisitors and the time of suspicious activity. As a result, sharing databetween multiple doorbell users can help reduce crime and theft inneighborhoods around the world.

Suspicious activity can be “tagged” and shared with members of a usergroup (e.g., a group of neighbors). The shared data can include photosand information regarding suspicious visitors. The information caninclude written descriptions, recorded descriptions, and videos. Forexample, a first doorbell can take a picture of a visitor. The doorbellcan send the picture to a remote computing device. A user of the remotecomputing device can see the visitor. Then, the user can enterinformation regarding the suspicious visitor into the remote computingdevice. The doorbell system can then share the information and thepicture of the visitor with a user group, which can include otherdoorbell users.

An administrator of the user group can be a “master user” who has theability to add other users to the user group. One way of adding users toa user group is to enter email addresses of prospective users into aremote computing device (e.g., into an “app” running on the remotecomputing device). This app can be the same app used by theadministrator to configure her doorbell.

In a user group section (e.g., a “neighborhood section”) of the app, auser can see who else is in her neighborhood. In some embodiments, thehome locations of prospective or current users are displayed on a map.Selecting prospective users can enable the administrator to add newusers to the user group.

When a user thinks a visitor is suspicious, the user can report thevisitor and the nature of the suspicious activity to the user group.Thus, the user can enter the visitor into an activity log such that theevent has a “suspicious” tag. The event can then be shared with theother users via email, text message, a push notifications, or anysuitable means. The event can be recorded in a user group activity list,which in some embodiments, is only visible to members of the user group(or at least is not visible to the general public). The event can alsobe listed in a history of events reported by a specific individual.Thus, users can see events they reported, and users can see eventsreported by all members of a user group.

Each event can include an icon. Selecting the icon can cause the eventto be shared with the user group. In some embodiments, icons are shownon a map that is displayed on a remote computing device. In this manner,users can see where suspicious visitors have been reported by members ofthe user group, and in some embodiments, by members of other usergroups.

In some embodiments, a user group is limited to a particularneighborhood. In other embodiments, user groups are not limited to aparticular neighborhood.

Visitor data from a user (or from a user group) can be shared with lawenforcement (e.g., police officers) or other safety personnel to helpkeep neighborhoods safe. A suspicious event reported by a first user canbe shared with a second user. The second user can then share the eventwith law enforcement. In some embodiments, the user who reports theevent to the user group also reports the event to law enforcement (e.g.,by selecting a button in the app).

The app can include a “distress button” configured to enable a user toalert law enforcement and user group members that something is wrong.Pressing the button on a remote computing device can cause a doorbellsystem to send a push notification to other users to notify them thathelp is needed. The push notification can also communicate the nature ofthe event and can enable users to see a picture of the visitor causingthe trouble.

FIG. 5 illustrates a neighborhood, which can include many buildings 300a, 300 b, 300 c. The buildings 300 a, 300 b, 300 c can be individualhomes or individual buildings (e.g., multiple single-family homes,multiple apartments coupled together, offices). The buildings 300 a, 300b, 300 c can be located next to each other or they can be separated byother homes or buildings.

Embodiments can include diverse ways of using a doorbell system 386,which can include multiple doorbells 202 a, 202 b, 202 c and multipleremote computing devices 204 a, 204 b, 204 c. Each doorbell 202 a, 202b, 202 c can be coupled to an exterior wall of a different building 300a, 300 b, 300 c. A different remote computing device 204 a, 204 b, 204 ccan configure each doorbell 202 a, 202 b, 202 c. Each building 300 a,300 b, 300 c can have its own wireless network 308 a, 308 b, 308 c.Another network 308 d (e.g., a cellular network, the Internet) canenable a first doorbell 202 a to send a picture of a visitor 388 a to asecond doorbell 202 b and/or to a second remote computing device 204 b.

A first doorbell 202 a can send a visitor notification (e.g., an alertas shown in FIG. 1) to a first computing device 204 a via a firstwireless network 308 a. In some embodiments, however, it is advantageousfor a doorbell 202 a or a remote computing device 204 a associated witha first building 300 a to send information regarding a visitor 388 a toa doorbell 202 b or a remote computing device 204 b associated with asecond building 300 b. In several embodiments, it is advantageous for adoorbell 202 a or a remote computing device 204 a associated with afirst building 300 a to receive information regarding a visitor 388 bfrom a doorbell 202 b or a remote computing device 204 b associated witha second building 300 b. An external network 308 d can facilitate thissending and receiving of information regarding visitors 388 a, 388 b.This way, the doorbell system 386 can enable notifying a second remotecomputing device 204 b regarding a visitor detected by a first doorbell202 a even though the second remote computing device 204 b is notconfigured to control the first doorbell 202 a.

Each of the doorbells 202 a, 202 b, 202 c illustrated in FIG. 5 caninclude a camera assembly 208 (as labeled in FIG. 1). Some embodimentsof using the doorbell system 386 include taking a first picture of afirst visitor 388 a with the first doorbell 202 a; sending the firstpicture to the first remote computing device 204 a; and indicating afirst trait (e.g., identity, suspicious behavior, bodilycharacteristics) of the first visitor 388 a via the first remotecomputing device 204 a.

The first remote computing device 204 a can be used to categorize thevisitor. For example, the user of the first remote computing device canindicate whether the first visitor 388 a is a salesperson, a fundraiser,or a potential criminal. The first remote computing device 204 a canshare this categorization with other members of the user group, whichcan include users of the remote computing devices 204 a, 204 b, 204 c.

A first user of the first remote computing device 204 a (e.g., the ownerof the first doorbell 202 a) can create a user group. The user group caninclude the first user of the first remote computing device 204 a and asecond user of a second remote computing device 204 b. Note that in FIG.5, the first remote computing device 204 a is located remotely relativeto the first doorbell 202 a because the first remote computing device isnot electrically or mechanically coupled to the first doorbell 202 a(even though the first remote computing device 204 a and the firstdoorbell 202 a are located in the same building 300 a).

Embodiments can also include sharing the first picture of the firstvisitor 388 a with the user group. The sharing of the first picture ofthe first visitor 388 a with the user group can be in response to thefirst trait of the first visitor 388 a. For example, the first trait canbe that the first visitor 388 a is acting suspiciously by peaking overfences or looking through windows.

Several embodiments include sending the first trait and the firstpicture of the first visitor 388 a to a database 390 configured toprovide information regarding the first visitor 388 a to the user group.The first doorbell 202 a can also determine a time at which the firstvisitor 388 a visited the first doorbell 202 a. A portion of thedoorbell system 386 can provide this time to the database 390.

Some embodiments include receiving data with the first remote computingdevice 204 a regarding a second doorbell 202 b that comprises a secondcamera and regarding a third doorbell 202 c that comprises a thirdcamera. As illustrated in FIG. 5, the first doorbell 202 a is coupled toa first building 300 a. The second doorbell 202 b is coupled to a secondbuilding 300 b. The third doorbell 202 c is coupled to a third building300 c. Doorbells can be mounted near a door in an entryway. Thebuildings 300 a, 300 b, and 300 c can be located apart from each othersuch that each building is a separate residential dwelling or a separateoffice space. The database 390 can be configured to share visitorinformation with the user group. Embodiments can include selecting (viathe first remote computing device 204 a) to receive the visitorinformation from at least one of the second doorbell 202 b and the thirddoorbell 202 c. Receiving the data can comprise receiving the visitorinformation from a different location than a first location of the firstbuilding 300 a.

Each doorbell 202 a, 202 b, and 202 c can include a camera assembly 208(labeled in FIG. 1). In several embodiments, a camera assembly 208 cantake videos or stationary images. Thus, a “picture” taken by a camera ofa doorbell can actually be a video. In some embodiments, the “picture”is a stationary image (rather than a video).

There are many ways to create user groups. In some embodiments, creatinga user group comprises adding a first email address and a second emailaddress to a database. The first email address can be associated withthe first doorbell 202 a. The second email address can be associatedwith a second doorbell 202 b. In some embodiments, a first user of afirst doorbell 202 a sends an invitation to join a doorbell user groupto a second user of a second doorbell 202 b. The first user can send theinvitation via a first remote computing device 204 a (that is authorizedto configure the first doorbell 202 a) to a second remote computingdevice 204 b (that is authorized to configure the second doorbell 202b). The second user can then accept or decline the invitation via thesecond remote computing device 204 b. In some embodiments, the seconduser accepts or declines the invitation to join the doorbell user groupat least partially in response to seeing the location of the firstdoorbell 202 a on the display of the second computing device 204 b. Forexample, if the first and second users are neighbors, then the seconduser could be more likely to accept the invitation than if the first andsecond users live much farther away from each other.

FIG. 6 illustrates a map 392 that is displayed by the first remotecomputing device 204 a. The map 392 displays a first location of thefirst doorbell 202 a, a second location of the second doorbell 202 b,and a third location of the third doorbell 202 c. The map 392 can alsoinclude other items such as street names. Several embodiments includedisplaying information regarding the second doorbell 202 b in responseto a person using the first computing device 204 a to select a secondicon representing the second doorbell 202 b while the second icon isdisplayed on the first remote computing device 204 a. (In FIG. 6,doorbells 202 a, 202 b, 202 c are represented by icons that look likedoorbells.) This information can include an address of the seconddoorbell 202 b, contact information (e.g., a name, a phone number, anemail) of a user of the second doorbell 202 b, and/or a picture of theuser of the second doorbell 202 b. Selecting the second icon can add asecond user of the second doorbell 202 b to the doorbell user group.

Not all members of a doorbell user group necessarily have a doorbell.Members of the user group who have not yet purchased a doorbell with acamera can still receive visitor information, including visitorpictures, on their remote computing devices. For example, a picturetaken by the first doorbell 202 a can be sent to the remote computingdevices of people who have not purchased a doorbell with a camera.

Several embodiments include selecting a first button 394 on the displayof the first remote computing device 204 a to alert law enforcementand/or to alert the user group. The button 394 can be a portion of thegraphical user interface of an app.

A first user can also join a user group that was previously created byanother user. This first user can couple a first doorbell having a firstcamera to a first building; configure the first doorbell to wirelesslycommunicate with a first remote computing device; and/or join a usergroup via the first remote computing device. This user group cancomprise a second user of a second doorbell having a second camera and athird user of a third doorbell having a third camera. The seconddoorbell can be configured to wirelessly communicate with a secondremote computing device. This first user can receive a first picture anda first trait of a first visitor with the first remote computing device.This first picture could have been taken previously by the seconddoorbell or the third doorbell. This first user can take a secondpicture of a second visitor with the first doorbell; and/or send thesecond picture of the second visitor to the user group such that thesecond remote computing device can display the second picture. Thisfirst user can detect a second visitor with the first doorbell. Thisfirst user can determine that the second visitor is the first visitor bya portion of the doorbell system analyzing the first picture from thesecond doorbell or the third doorbell. This analysis can include thedoorbell system comparing the first picture to the second picture.Embodiments can also include alerting a first user of the first doorbellthat the second visitor is the first visitor (i.e., the first visitor isthe same person as the second visitor).

FIG. 7 illustrates that a first doorbell 202 a can take a picture 398.Then, the first doorbell 202 a can send the picture 398 to a firstremote computing device 204 a. (The doorbell 202 a can send the picture398 directly to the first remote computing device 204 a or indirectly tothe first remote computing device 204 a via an intermediary device suchas a router, server, network, and/or the Internet.) Then, the firstremote computing device 204 a can send the picture 398 to a secondremote computing device 204 b. This approach enables the second remotecomputing device 204 b to receive the picture 398 even though the secondremote computing device is not communicatively coupled to the doorbell202 a.

In contrast, FIG. 8 illustrates an embodiment in which multiple remotecomputing devices 204 a, 204 b, 204 c are communicatively coupled withone doorbell 202 a. Thus, the doorbell 202 a can send a picture that ittakes to all of the remote computing devices 204 a, 204 b, 204 c. Insome cases, a first user might not want her doorbell to becommunicatively coupled with a neighbor's remote computing device (e.g.,because communicatively coupling her doorbell with her neighbor's remotecomputing device could enable the neighbor to see visitors and/or talkwith visitors to the home of the first user without the first user'spermission). As a result, the first user might want to be able to sharea visitor picture and/or visitor information with a neighbor without theneighbor's remote computing device being communicatively coupled withthe first user's doorbell. The first user's remote computing device, auser group, a server and/or a database can act as a gatekeeper thatenables the first user to control what visitor information she shareswith other members of a user group (e.g., with neighbors or members ofother households).

In some embodiments, a homeowner can share information from her doorbellwith neighbors' remote computing devices via the doorbell user group 400(shown in FIG. 10) even though the neighbors' remote computing devicesare not configured to receive visitor alerts from the homeowner'sdoorbell each time the homeowner's doorbell detects a visitor (e.g., viamotion detection or button press detection). Some embodiments includethe homeowner (e.g., a user) choosing to send a first visit information(regarding a first visitor) to neighbor's remote computing devices andchoosing not to send a second visit information (regarding a secondvisitor) to neighbor's remote computing devices. This choosing step canbe after and in response to seeing (e.g., displaying) the visitors on aremote computing device. Thus, the system 408 (shown in FIG. 10) enablesa user to selectively decide what visit information to share withmembers of the doorbell user group.

In contrast, the configuration illustrated in FIG. 8 does not enableselectively deciding what visit information to share. Instead, all theremote computing devices 204 a, 204 b, 204 c receive the visitinformation. While the configuration illustrated in FIG. 8 may work wellfor one household, it typically does not work well with multiplehouseholds (e.g., an entire neighborhood) due to privacy concerns anddue to the fact that most neighbors would not want to receive anotification every time a person approaches any home in theneighborhood. The number of unhelpful notifications would be verybothersome. Imagine how many uneventful notifications a user wouldreceive each day after school as dozens of children come home. Thus, thesystem 408 illustrated in FIG. 10 works much better than the systemillustrated in FIG. 8 when multiple households, homes, and/or buildingsare involved in the visitor information sharing.

For example, as shown in FIG. 11, the remote computing device 204 band/or the user group 400 can act as a gatekeeper system to enable auser to select which visitor information is shared other remotecomputing devices 204 a, 204 c after the user's remote computing device204 b receives the visitor information. This approach allows a user toshare (e.g., by selecting a button on the device 204 b) informationregarding some visitors (e.g., suspicious visitors) with other remotecomputing devices 204 a, 204 c after seeing (or displaying) the visitorson the computing device 204 b. This approach also allows the user to notshare information regarding other visitors (e.g., trusted friends) withother remote computing devices 204 a, 204 c after seeing (or displaying)the other visitors on the computing device 204 b. Thus, the “sharedecision” can be in response to the user seeing (e.g., analyzing) thevisitors on her remote computing device 204 b.

In contrast, the system shown in FIG. 8 does not include a visitor byvisitor “share decision.” Instead, a user simply adds several computingdevices 204 a, 204 b, 204 c to a system such that the computing devices204 a, 204 b, 204 c receive a visitor notification (e.g., an alert) eachtime the doorbell 202 a detects a visitor in response to the computingdevices 204 a, 204 b, 204 c being communicatively coupled with thedoorbell 202 a.

FIG. 9 illustrates an embodiment in which a remote computing device 204a is communicatively coupled (e.g., wirelessly) with multiple doorbells202 a, 202 b, 202 c. For example, a first user could be able to seeand/or talk with visitors detected by her own doorbell 202 a or detectedby neighbors' doorbells 202 b, 202 c. This approach raises privacyconcerns.

FIG. 10 illustrates a diagrammatic view of an embodiment that includes auser group 400. The user group 400 can include a database 390, a server404, and user information 406 such as email addresses, user profiles,and user doorbell locations.

Thus, many embodiments enable members of a user group to share visitorinformation with each other without granting doorbell control to membersof the user group. For example, a first user can alter at least onesetting (e.g., a chime tone, a greeting, a silent mode, on-demand videomodes) of her doorbell but typically cannot alter settings of neighbors'doorbells (e.g., of other doorbells in the user group). Theseembodiments enable a first user to determine what visitor pictures andinformation her doorbell shares with a user group.

The doorbell system 408 can include a first remote computing device 204a communicatively coupled to a first doorbell 202 a that has a firstcamera 208 (labeled in FIG. 1). Some embodiments include sending a firstpicture 410, taken by the first doorbell 202 a, of a first visitor 402 ato the first remote computing device 204 a. An arrow indicates the firstdoorbell 202 a is communicatively coupled with the first remotecomputing device 204 a. This communicatively coupling can be wirelessand can include two-way communication to enable the first remotecomputing device 204 a to send data and doorbell setting parameters tothe first doorbell 202 a.

The first doorbell 202 a is not communicatively coupled to the secondremote computing device 204 b even though the second remote computingdevice 204 b can receive a picture taken by the first doorbell 202 afrom at least a portion of the user group 400. This way, the secondremote computing device 204 b can receive information regarding avisitor detected by the first doorbell 202 a, but the second remotecomputing device 204 b cannot alter settings of the first doorbell 202a, initiate on-demand videos from the first doorbell 202 a, or talk withthe first visitor 402 a via the first doorbell 202 a.

Embodiments can include creating a doorbell user group 400 comprising afirst user of the first remote computing device 204 a and a second userof the second remote computing device 204 b, which is communicativelycoupled to a second doorbell 202 b (as shown by the arrow) but is notcommunicatively coupled to the first doorbell 202 a. The remotecomputing devices 204 a, 204 b, 204 c can be communicatively coupledwith the user group 400 to enable sharing visitor information (e.g.,pictures, audio files, visitor descriptions) detected by one of thedoorbells 202 a, 202 b, 202 c (and/or recorded by one of the remotecomputing devices 204 a, 204 b, 204 c) with all of the remote computingdevices 204 a, 204 b, 204 c communicatively coupled with the user group400. This way, visitor information can be shared with members of theuser group 400 without users being concerned that other members of theuser group 400 might hear private visitor conversations and/or seeconfidential visitors. Embodiments can enable a user to control whatvisitor information members of the user group receive from the user'sdoorbell.

Embodiments can include sharing the first picture 410 of the firstvisitor 402 a with the doorbell user group 400 such that the secondremote computing device 204 b receives the first picture 410 taken bythe first doorbell 202 a. Sharing the first picture 410 with thedoorbell user group 400 can require the user of the first remotecomputing device 204 a to authorize sharing the first picture (and/orother information regarding the first visitor 402 a) with the user group400.

As illustrated in FIG. 10, the first remote computing device 204 a isnot communicatively coupled to the second doorbell 202 b. Embodimentscan include receiving, by the first remote computing device 204 a, asecond picture 412 taken by the second doorbell 202 b in response to thesecond doorbell 202 b sending the second picture 412 to a database 390configured to provide visitor information 406 to the doorbell user group400.

The visitors 402 a, 402 b, 402 c can be the same person. For example, asolicitor knocking on doors of buildings 300 a, 300 b, 300 c in aneighborhood can be detected by motion sensors of many doorbells 202 a,202 b, 202 c. In some cases, visitors 402 b, 402 c can be differentpeople.

FIG. 11 illustrates a diagrammatic view of an embodiment that includes auser group 400. Using a doorbell system 408 can include coupling a firstdoorbell 202 a having a first camera 208 (labeled in FIG. 1) to a firstbuilding 300 a. The first building 300 a can include a first wirelessnetwork 308 a that communicatively couples the first doorbell 202 a tothe first remote computing device 204 a, but does not communicativelycouple the first doorbell 202 a to a second remote computing device 204b.

In some embodiments, the doorbell 202 a is connected to the firstwireless 308 a, which connects to the Internet and/or to a cellularnetwork to enable the first doorbell 202 a to be communicatively coupledto the first remote computing device 204 a even when the first remotecomputing device 204 a is many miles away from the first building 300 a.In some cases, when the first remote computing device 204 a is locatedwithin range of the first wireless network 308 a (e.g., inside the firstbuilding 300 a), the first wireless network 308 a can directlycommunicatively couple the first doorbell 202 a to the first remotecomputing device 204 b. The second building 300 b can include a secondwireless network 308 b, which can communicatively couple the seconddoorbell 202 b to the second remote computing device 204 b. The thirdbuilding 300 c, to which the third doorbell 202 c can be mechanicallycoupled, can include a third wireless network 308 c.

Several embodiments include configuring the first doorbell 202 a towirelessly communicate with the first remote computing device 204 a.Some embodiments include joining, by the first remote computing device204 a, a doorbell user group 400 that comprises a second user of thesecond doorbell 202 b having a second camera coupled to the secondbuilding 300 b. The doorbell user group 400 can also include a thirduser of a third doorbell 202 c having a third camera coupled to thethird building 300 c. The second doorbell 202 b can be configured towirelessly communicate with the second remote computing device 204 b.

Some embodiments include receiving, by the first remote computing device204 a, a first visitor picture 410 that was taken by the second doorbell202 b or the third doorbell 202 c. For example, arrow 416 shows how thefirst visitor picture 410 from the second doorbell 202 b can be sent tothe second remote computing device 204 b and/or to the user group 400(in some cases without passing through the second remote computingdevice 204 b). Arrow 418 represents that the second remote computingdevice 204 b can send the first picture 410 to the user group 400 and/orcan send permission for members of the user group 400 to view the firstpicture 410 to the user group 400. Arrow 420 represents how the usergroup 400 can send the first picture 410 to the first remote computingdevice 204 a and/or to the third remote computing device 204 c.

As used herein, “user groups” often do not include humans, but insteadinclude devices owned by various humans. For example, a neighborhoodassociation may decide to purchase doorbells 202 a, 202 b, 202 c.Creating a doorbell user group can include communicatively coupling thedoorbells 202 a, 202 b, 202 c and the remote computing devices 204 a,204 b, 204 c as shown in FIG. 10. As a result of this communicativelycoupling, members of the neighborhood association can share visitorinformation. A doorbell user group can include the doorbells 202 a, 202b, 202 c and/or the remote computing devices 204 a, 204 b, 204 c. Usergroups 400 can include databases 390, servers 404, and information 406regarding the owners of the doorbells 202 a, 202 b, 202 c and the remotecomputing devices 204 a, 204 b, 204 c. User groups 400 can include thelocations of each doorbell in the user group 400. User groups 400 canstore visitor pictures and visitor information for future reference bymembers of the user groups 400.

Referring now to FIG. 11, embodiments can include receiving from thedoorbell user group 400, by the first remote computing device 204 a, thefirst visitor picture 410 taken by the second doorbell 202 b even thoughthe first remote computing device 204 a is not communicatively coupledto the second doorbell 202 b. Embodiments can also include receiving, bythe first remote computing device 204 a, a first trait regarding a firstvisitor 402 a in response to a second user of the second remotecomputing device 204 b inputting the first trait into the second remotecomputing device 204 b. For example, the second user can label the firstvisitor 402 as “suspicious” and/or can record a description of the firstvisitor 402 a.

Several embodiments include taking a second visitor picture 412, by thefirst doorbell 202 a, and sending the second visitor picture 412 to thedoorbell user group 400 such that the second remote computing device 204b and the third remote computing device 204 c can display the secondvisitor picture 412 even though the second remote computing device 204 band the third remote computing device 204 c are not communicativelycoupled to the first doorbell 202 a

The doorbell user group 400 can comprise a database 390 that includesmany visitor pictures taken by more doorbells that are communicativelycoupled to the doorbell user group 400. The database 390 can include afirst visitor picture 410 taken by the second doorbell 202 b of thesecond building 300 b. The first doorbell 202 a of the first building300 a can take a second visitor picture 412. At least a portion of thedoorbell system 408 can determine that the first visitor picture 410 andthe second visitor 412 picture show a visitor (i.e., show the sameperson). Embodiments can include labeling the visitor with solicitorinformation such that members of the doorbell user group 400 can see thefirst visitor picture 410 associated with the solicitor information. Forexample, the remote computing devices 204 a, 204 b, 204 c can downloadthe first visitor picture 410 (or another visitor picture) andinformation regarding the visitor's solicitation behavior. The remotecomputing devices 204 a, 204 b, 204 c can display the solicitorinformation along with the picture of the solicitor.

Users can type information regarding visitors into their remotecomputing devices 204 a, 204 b, 204 c. The user group 400 can then sharethis information with members of the user group 400. Some embodimentsinclude alerting the members regarding at least a portion of thesolicitor information. This alert 422 can include a picture of thesolicitor and other information regarding the solicitor. Severalembodiments include receiving a solicitor alert 422 in response to thesecond doorbell 202 b of the second building 300 b and the thirddoorbell 202 c of the third building 300 c detecting a visitor (e.g.,detecting the same person within a predetermined time, which can bewithin 24 hours).

The alerts 422 shown in FIG. 11 can also be burglary alerts. Someembodiments include sending an alert 422 to members of the doorbell usergroup 400 in response to detecting a burglary of the first building 300a. A remote burglar detection system (e.g., a remote sensor 242 of analarm system), can detect the burglary. The remote sensor 424 can alsobe a fire alarm or smoke alarm. Some embodiments include sending analert 422 to members of the doorbell user group 400 in response to aremote sensor 424 detecting fire and/or smoke.

A doorbell system 408 can comprise a first doorbell 202 a having a firstcamera coupled to a first building 300 a, wherein the first doorbell 202a is communicatively coupled to a first remote computing device 204 a; asecond doorbell 202 b having a second camera coupled to a secondbuilding 300 b, wherein the second doorbell 202 b is communicativelycoupled to a second remote computing device 204 b; and a doorbell usergroup 400 comprising a database 390 having images 410, 412 taken by thefirst camera and the second camera. The doorbell user group 400 can becommunicatively coupled to the first remote computing device 204 a andthe second remote computing device 204 b.

In several embodiments, the first doorbell 202 a is not communicativelycoupled to the second remote computing device 204 b, and the seconddoorbell 202 b is not communicatively coupled to the first remotecomputing device 204 a while the system 408 is configured such that thefirst remote computing device 204 a receives a first visitor picture 410taken by the second doorbell 202 b via the doorbell user group 400. Asecond visitor picture 412 can be taken by the first doorbell 202 a anddisplayed by the second remote computing device 204 b.

The doorbell system 408 can also include a remote sensor 424 configuredto monitor the first building 300 a and detect an unauthorized buildingintrusion. The doorbell system 408 can include at least one alert 422sent to the doorbell user group 400 in response to the remote sensor 424detecting the unauthorized building intrusion.

Several embodiments include a solicitor alert sent to the doorbell usergroup 400 in response to a visitor being detected by the first doorbell202 a at the first building 300 a and by the second doorbell 202 b atthe second building 300 b.

Information collected from the doorbells 202 a, 202 b, 202 c can beanalyzed (e.g., by the system). An alert 422 can be send to remotecomputing devices 204 a, 204 c in response to analytics based on thecollected information.

Aggregated doorbell information can be analyzed to look for trends andabnormal behaviors that might be correlated with crime or other unwantedbehavior. Analytics can include the number of visits or visitors to aparticular building, group of buildings, or area. For example, a highnumber of unique visitors could suggest an illegal business is beingoperated out of a home (e.g., drug dealing). Analytics can also evaluatehow long visitors wait at a door before leaving. In some cases,analytics include determining whether a person with a criminal historyor arrest warrant is contacting more than one building in an area withina predetermined time.

Several embodiments include taking, by the second doorbell 202 b, afirst visitor picture 410; sending, by the second doorbell 202 b, thefirst visitor picture to the user group; and comparing, by the usergroup 400, the first visitor picture 410 to criminal pictures of adatabase 390. A moderator (e.g., a person who acts as an administratorof the user group 400) can compare visitor pictures to determine if thepictures show the same person (e.g., a solicitor) or show a criminal.Some embodiments use computer image recognition to compare images.

The first building 300 a can include an alarm 434 that can be locatedremotely relative to the first doorbell 202 a. In some embodiments, thedoorbell 202 a is communicatively coupled to the alarm 434. The alarm434 can include a speaker and electronics configured to enable thespeaker to emit an alarm sound.

A button on the user interface of the first remote computing device 204a can enable a user to active the alarm 434. In response to a signalfrom the remote sensor 424, the system 408 can enter an Alarm State,which can include recording, by the first doorbell 202 a, a video;blinking a light 216, 220 (shown in FIG. 1) of the first doorbell 202 a;and emitting an alarm sound from a speaker 488 (shown in FIG. 4) of thefirst doorbell 202 a. Other members of the user group 400 can receive analert 422 regarding the Alarm State. Other members can also see aflashing light and hear the alarm sound from the first doorbell 202 a.As a result, the first doorbell 202 a can serve as a beacon to firstresponders, which can include neighbors, medical personnel, and lawenforcement officers.

Each member of the user group 400 can choose which members receivealerts, visitor pictures, and visitor information from the choosingmember. This approach enables sub-groups within a larger user group.

Interpretation

None of the steps described herein is essential or indispensable. Any ofthe steps can be adjusted or modified. Other or additional steps can beused. Any portion of any of the steps, processes, structures, and/ordevices disclosed or illustrated in one embodiment, flowchart, orexample in this specification can be combined or used with or instead ofany other portion of any of the steps, processes, structures, and/ordevices disclosed or illustrated in a different embodiment, flowchart,or example. The embodiments and examples provided herein are notintended to be discrete and separate from each other.

The section headings and subheadings provided herein are nonlimiting.The section headings and subheadings do not represent or limit the fullscope of the embodiments described in the sections to which the headingsand subheadings pertain. For example, a section titled “Topic 1” mayinclude embodiments that do not pertain to Topic 1 and embodimentsdescribed in other sections may apply to and be combined withembodiments described within the “Topic 1” section.

Some of the devices, systems, embodiments, and processes use computers.Each of the routines, processes, methods, and algorithms described inthe preceding sections may be embodied in, and fully or partiallyautomated by, code modules executed by one or more computers, computerprocessors, or machines configured to execute computer instructions. Thecode modules may be stored on any type of non-transitorycomputer-readable storage medium or tangible computer storage device,such as hard drives, solid state memory, flash memory, optical disc,and/or the like. The processes and algorithms may be implementedpartially or wholly in application-specific circuitry. The results ofthe disclosed processes and process steps may be stored, persistently orotherwise, in any type of non-transitory computer storage such as, e.g.,volatile or non-volatile storage.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and subcombinations are intended to fall withinthe scope of this disclosure. In addition, certain method, event, state,or process blocks may be omitted in some implementations. The methods,steps, and processes described herein are also not limited to anyparticular sequence, and the blocks, steps, or states relating theretocan be performed in other sequences that are appropriate. For example,described tasks or events may be performed in an order other than theorder specifically disclosed. Multiple steps may be combined in a singleblock or state. The example tasks or events may be performed in serial,in parallel, or in some other manner. Tasks or events may be added to orremoved from the disclosed example embodiments. The example systems andcomponents described herein may be configured differently thandescribed. For example, elements may be added to, removed from, orrearranged compared to the disclosed example embodiments.

Conditional language used herein, such as, among others, “can,” “could,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements and/orsteps. Thus, such conditional language is not generally intended toimply that features, elements and/or steps are in any way required forone or more embodiments or that one or more embodiments necessarilyinclude logic for deciding, with or without author input or prompting,whether these features, elements and/or steps are included or are to beperformed in any particular embodiment. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list. Conjunctivelanguage such as the phrase “at least one of X, Y, and Z,” unlessspecifically stated otherwise, is otherwise understood with the contextas used in general to convey that an item, term, etc. may be either X,Y, or Z. Thus, such conjunctive language is not generally intended toimply that certain embodiments require at least one of X, at least oneof Y, and at least one of Z to each be present.

The term “and/or” means that “and” applies to some embodiments and “or”applies to some embodiments. Thus, A, B, and/or C can be replaced withA, B, and C written in one sentence and A, B, or C written in anothersentence. A, B, and/or C means that some embodiments can include A andB, some embodiments can include A and C, some embodiments can include Band C, some embodiments can only include A, some embodiments can includeonly B, some embodiments can include only C, and some embodiments caninclude A, B, and C. The term “and/or” is used to avoid unnecessaryredundancy.

While certain example embodiments have been described, these embodimentshave been presented by way of example only, and are not intended tolimit the scope of the inventions disclosed herein. Thus, nothing in theforegoing description is intended to imply that any particular feature,characteristic, step, module, or block is necessary or indispensable.Indeed, the novel methods and systems described herein may be embodiedin a variety of other forms; furthermore, various omissions,substitutions, and changes in the form of the methods and systemsdescribed herein may be made without departing from the spirit of theinventions disclosed herein.

The following is claimed:
 1. A method of using a doorbell systemcomprising a first doorbell coupled to a first building and a seconddoorbell coupled to a second building, wherein the first doorbellincludes a first camera and the first doorbell is configured towirelessly communicate with a first remote computing device, and whereinthe second doorbell includes a second camera and the second doorbell isconfigured to wireles sly communicate with a second remote computingdevice, the method comprising: receiving, by a doorbell user group, afirst wireless communication from the first remote computing device,wherein the first wireless communication comprises a request to join thedoorbell user group; transmitting, by the doorbell user group, a secondwireless communication from the first remote computing device to thesecond remote computing device, wherein the second wirelesscommunication comprises an invitation to join the doorbell user group,and wherein the first remote computing device is communicatively coupledto the first doorbell, and the first remote computing device is notdirectly communicatively coupled to the second doorbell; receiving, bythe doorbell user group, a selection of at least one of a first icon, asecond icon, and a third icon, wherein the first icon indicates a firstlocation of the first doorbell, the second icon indicates a secondlocation of the second doorbell, and the third icon indicates a thirdlocation of a third doorbell, wherein at least one of the first icon,the second icon, and the third icon is shown on a map display loaded onthe first remote computing device; and in response to receiving theselection of at least one of the first icon, the second icon, and thethird icon, adding at least one of the first doorbell, the seconddoorbell, and the third doorbell to the doorbell user group.
 2. Themethod of claim 1, wherein the doorbell user group further comprises athird doorbell having a third camera coupled to a third building, themethod further comprising sending, by the doorbell user group, a firstvisitor picture to the first remote computing device, wherein the seconddoorbell or the third doorbell took the first visitor picture.
 3. Themethod of claim 2, further comprising selecting, by a first user of thefirst remote computing device, at least one of a second user of thesecond remote computing device and a third user of a third remotecomputing device, to receive at least one of an alert, a visitorpicture, and visitor information from the first user.
 4. The method ofclaim 1, further comprising sending, from the doorbell user group, tothe first remote computing device, a solicitor alert in response to boththe first doorbell and the second doorbell detecting a first person,wherein the solicitor alert comprises a first visitor picture.
 5. Themethod of claim 4, further comprising sending, by the doorbell usergroup, a first trait to the first remote computing device in response tothe second remote computing device receiving the first trait, whereinthe first trait is regarding a first visitor.
 6. The method of claim 4,further comprising taking, by the first doorbell, a second visitorpicture, and sending the second visitor picture to the doorbell usergroup such that the second remote computing device can display thesecond visitor picture, wherein the second remote computing device isnot directly communicatively coupled to the first doorbell.
 7. Themethod of claim 6, wherein at least one of the first visitor picture anda second visitor picture comprises a video.
 8. The method of claim 6,wherein at least one of the first visitor picture and the second visitorpicture comprises a video feed that is less than five minutes old. 9.The method of claim 1, wherein the doorbell user group comprises adatabase having a first visitor picture taken by the second doorbell ofthe second building, the method further comprising taking, by the firstdoorbell of the first building, a second visitor picture, anddetermining, by a portion of the doorbell system, that the first visitorpicture and the second visitor picture show a visitor.
 10. The method ofclaim 9, further comprising labeling the visitor with solicitorinformation such that members of the doorbell user group can see thefirst visitor picture associated with the solicitor information.
 11. Themethod of claim 10, further comprising alerting the members of thedoorbell user group regarding at least a portion of the solicitorinformation.
 12. The method of claim 9, further comprising providing, bya portion of the doorbell system and to the database, a time at whichthe visitor visited the first doorbell.
 13. The method of claim 1,further comprising adding, to the doorbell user group, solicitationinformation regarding a visitor of a first visitor picture.
 14. Themethod of claim 1, further comprising sending an alert to members of thedoorbell user group in response to detecting, by a remote burglardetection system, a burglary of the first building.
 15. The method ofclaim 1, further comprising sending an alert to members of the doorbelluser group in response to detecting, by a remote sensor, at least one ofsmoke and fire.
 16. The method of claim 1, wherein creating the doorbelluser group comprises adding a first email address and a second emailaddress to a database, wherein the first email address is associatedwith the first doorbell and the second email address is associated withthe second doorbell.
 17. The method of claim 16, further comprisingadding, by an administrator of the doorbell user group, the first emailaddress and the second email address to the database.
 18. The method ofclaim 17, wherein the administrator of the doorbell user group adds thefirst email address and the second email address to the database via aremote computing device.
 19. The method of claim 1, wherein the doorbelluser group comprises at least one of a database, a server, and userinformation about at least one of a first user of the first remotecomputing device, a second user of a second remote computing device, anda third user of a third remote computing device.
 20. The method of claim19, wherein the user information comprises at least one of an emailaddress of the first user, an email address of the second user, an emailaddress of the third user, a user profile of the first user, a userprofile of the second user, a user profile of the third user, a locationof the first doorbell, a location of the second doorbell, and a locationof a third doorbell.